Skip to content
This repository was archived by the owner on Jan 23, 2026. It is now read-only.

Uboot prompt#631

Merged
mangelajo merged 2 commits intojumpstarter-dev:mainfrom
michalskrivanek:uboot-prompt
Sep 22, 2025
Merged

Uboot prompt#631
mangelajo merged 2 commits intojumpstarter-dev:mainfrom
michalskrivanek:uboot-prompt

Conversation

@michalskrivanek
Copy link
Copy Markdown
Contributor

fixes wrong behavior in reading uboot output and sending commands

@netlify
Copy link
Copy Markdown

netlify Bot commented Sep 19, 2025

Deploy Preview for jumpstarter-docs ready!

Name Link
🔨 Latest commit 6b80743
🔍 Latest deploy log https://app.netlify.com/projects/jumpstarter-docs/deploys/68cd7698060cec0008ce8b39
😎 Deploy Preview https://deploy-preview-631--jumpstarter-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@mangelajo
Copy link
Copy Markdown
Member

@michalskrivanek also confirms that he manually tested the flashers on renesas and TI for which we have no good E2E yet.

@michalskrivanek
Copy link
Copy Markdown
Contributor Author

well, "confirmed" as much as i could:)
we do have boards that start with the "bootmenu" that adds escape sequences to the output (e.g. screen dimension probing sequence) and at least on some versions of uboot when exitting from menu it's not a clear "new line" + "=>", but rather a "=>". for this reason i hardcoded the previous behavior to the reboot_to_console(). I don't think the cmdline is actually configurable so the whole prompt variable in driver is probably not-so-useful anyway.

Comment thread packages/jumpstarter-driver-uboot/jumpstarter_driver_uboot/client.py Outdated
Copy link
Copy Markdown
Member

@mangelajo mangelajo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small nit

@michalskrivanek michalskrivanek force-pushed the uboot-prompt branch 2 times, most recently from 037a695 to 5ce1200 Compare September 19, 2025 14:56
some commands print strings resembling the prompt, e.g.:
=> crc32 0x48000000 0xc8438; echo $?
crc32 for 48000000 ... 480c8437 ==> bd70c7dc
we send "\n" before every command to make sure we have a clean prompt. But in doing so we mistakenly re-execute the previous command. That seems ot be the unfortunate u-boot shell behavior. Let's type "#\n" that "runs" an empty command that doesn't do anything and has the same clean prompt response we want.
@mangelajo mangelajo merged commit 5411b73 into jumpstarter-dev:main Sep 22, 2025
17 checks passed
@michalskrivanek michalskrivanek deleted the uboot-prompt branch September 25, 2025 10:35
@jumpstarter-backport-bot
Copy link
Copy Markdown

Successfully created backport PR for release-0.7:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants